Don't suffer with ugly layouts! Clean it up with the
Theme Studio!
http://filemakerthemes.com/downloads

1. New Videos Released

   "The Separation Model - Part 10 - Calendars Everywhere"
       and
   "The Separation Model - Part 11 - Reporting Separated"

---------------------------------------------
#1. NEW VIDEOS:
---------------------------------------------

   The Separation Model - Part 10 - Calendars Everywhere
   ------------------------------------------

   In this video in the series, we're again laying some
   groundwork for future videos which deal with "separation
   issues". The content covered isn't super specified to
   the Separation Model, but does provide a wealth of
   knowledge about integrating a vital feature which is
   inevitably added to most any database - calendar
   widgets.

   Even if your database never deals with scheduling
   events, you're going to need to filter out information
   based on dates, times and date/time ranges - if only for
   reporting purposes.

   In order to make this happen, you'll often need some
   form of a calendar widget. Yeah, FileMaker does provide
   a great little calendar widget which can be used right
   on fields - and you may be able to get by with that
   alone - but really, "Why stop there?". Once you've
   implemented the calendar widget solution from this
   video, you may be hard pressed to use any other method.
   It's universal, it's flexible and quite powerful. Here's
   a hint, "Use a 'Calendar' utility table." Watch the
   video for more useful information!

http://www.filemakermagazine.com/videos/ the-separation-model-part-10-calendars-everywhere.html

~~~~

   The Separation Model - Part 11 - Reporting Separated
   --------------------------------------------------

   Reporting is one of the most field hungry things you can
   ever do within FileMaker. So, what do I mean by field
   hungry? Well, take your standard timestamp value for
   example. It's composed of many different pieces of
   information - many you may want to report on. It has a
   day name, day value, month name, month value, month
   number, year number, hours, minutes, seconds and maybe
   even a time zone.

   WOW! That's a lot of extra fields. I count at least ten
   different additional fields. I'd really hate to add even
   a portion of these extra fields to any data table which
   requires them for reporting. It's just a lot of extra
   "cruft" in my data file.

   So what are the options? Well, to give you a hint, you
   can easily create a "Reporting" file and do everything
   within that dedicated file. In fact, in many cases this
   is a very safe and sound solution.

   Then again, we have to take into account what our
   deployment model is. This is really the determining
   factor of how we're going to report. Is the UI file on
   the client device or being shared on the server? Do we
   want to maintain older reports so they can be printed in
   the future? Are we going to save a PDF version, save the
   data or simply use the original data? Will the original
   data change?

   What about what's needed in order to print the report?
   How about security and access? Should all users be able
   to see, access and print all reports in the system?

   These are all questions you'll have to ask of yourself
   when designing your own system. In this video I give you
   a ton of solid information about how printing might work
   in the Data Separation model. Give it a watch!

http://www.filemakermagazine.com/videos/ the-separation-model-part-11-reporting-separated.html

~~~~

Have a GREAT TIP? Seeking free access to the magazine?

We'll give you 3 months of free access
for your FileMaker Pro tips!

Send them to editor@filemakermagazine.com

Enjoy the article!

Matt Petrowsky
Editor - ISO FileMaker Magazine